Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release: Prerelease 7.6.0-beta.3 #25007

Closed
wants to merge 644 commits into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 28, 2023

This is an automated pull request that bumps the version from 7.6.0-beta.2 to 7.6.0-beta.3.
Once this pull request is merged, it will trigger a new release of version 7.6.0-beta.3.
If you're not a core maintainer with permissions to release you can ignore this pull request.

To do

Before merging the PR, there are a few QA steps to go through:

  • Add the "freeze" label to this PR, to ensure it doesn't get automatically forced pushed by new changes.
  • Add the "ci:daily" label to this PR, to trigger the full test suite to run on this PR.

And for each change below:

  1. Ensure the change is appropriate for the version bump. E.g. patch release should only contain patches, not new or de-stabilizing features. If a change is not appropriate, revert the PR.
  2. Ensure the PR is labeled correctly with one of: "BREAKING CHANGE", "feature request", "bug", "maintenance", "dependencies", "documentation", "build", "unknown".
  3. Ensure the PR title is correct, and follows the format "[Area]: [Summary]", e.g. "React: Fix hooks in CSF3 render functions". If it is not correct, change the title in the PR.
    • Areas include: React, Vue, Core, Docs, Controls, etc.
    • First word of summary indicates the type: “Add”, “Fix”, “Upgrade”, etc.
    • The entire title should fit on a line

This is a list of all the PRs merged and commits pushed directly to next, that will be part of this release:

  • 🐛 Bug: Test: Downgrade @testing-library/user-event to 14.3.0 #25004
  • 🐛 Bug: Webpack5: Only load babel config when babel-loader is used #25002
  • 🐛 Bug: Next.js: Fix react-docgen usage with preset-env settings #24993
  • 🔧 Maintenance: Docs: Changes corresponding to docs design updates #24925
  • 🐛 Bug: Test Build: Filter out addon-docs from essentials in the test build #24994
  • 🐛 Bug: Next.js: Fix Fast Refresh config for SWC mode #24991
  • 🏗️ Build: Storybook v8.0.0 initial merge #24271
  • 🏗️ Build: Sandbox: Add required flags to create-svelte-with-args CLI for SvelteKit #24990 (will also be patched)
  • 📝 Documentation: Docs: Storybook SWC builder updates #24986
  • 📝 Documentation: Update controls.md #23485
  • 📝 Documentation: Docs: Visual snaphot test changes #24954

If you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.

Feel free to manually commit any changes necessary to this branch after you've done the last re-generation, following the Make Manual Changes section in the docs, especially if you're making changes to the changelog.

When everything above is done:


Generated changelog

7.6.0-beta.3

cdedreuille and others added 30 commits October 18, 2023 11:13
StoryShots: Remove addon-storyshots from monorepo
Dependencies: Upgrade monorepo to TS5
Build: Remove StoyStore V6 sandbox templates
The state merging of useAddonState needed a fix because the merger function wasn't called with the correct data, due to react18 using async rendering, making this.state be the old state.
@github-actions github-actions bot added the release For PRs that trigger new releases. Automated label Nov 28, 2023
@JReinhold JReinhold added the freeze Freeze the Release PR with this label label Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
freeze Freeze the Release PR with this label release For PRs that trigger new releases. Automated
Projects
None yet
Development

Successfully merging this pull request may close these issues.